home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
iBrowse Update Disc
/
iBrowse Update Disc.iso
/
distrib
/
man
/
Manuals
/
Omniclient
/
3_BootNet
< prev
next >
Wrap
Text File
|
1998-02-04
|
5KB
|
118 lines
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<TITLE>!BootNet and Setstation</TITLE>
<META NAME="GENERATOR" CONTENT="Internet Assistant for Microsoft Word 2.04z">
</HEAD>
<BODY BGCOLOR="#FFFFFF">
<P>
<A HREF="2_useomni"><IMG SRC="pics/PREV.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="Front"><IMG SRC="pics/FRONT.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="TOC"><IMG SRC="pics/CONTS.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="index"><IMG SRC="pics/INDEX.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="4_TCPintro"><IMG SRC="pics/NEXT.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<H1>3 !BootNet and SetStation</H1>
<HR>
<H2><A NAME="Boot">Boot</A>Net</H2>
<P>
BootNet is an application that loads the software modules required
to allow Level4-type access over Ethernet and help establish the
IP address of the station for use with AUN.
<P>
!BootNet may be run
<UL>
<LI>on start-up to allow Ethernet access to Level 4 file servers
<LI>after !Internet is run, when Level 4 file servers are used
on a configured TCP/IP network.
</UL>
<P>
Normally this software is loaded automatically from the Ethernet
card ROM or from system ROM, except when it is run after !Internet
where the !BootNet application is required.
<P>
Where the software is resident on Ethernet card ROM, then the
modules are loaded if the configuration requires it: <TT><FONT FACE="Courier">*Configure
BootNet on</FONT></TT> loads the modules from Ethernet Card ROM,
but on an Acorn Access card some of the modules are loaded even
if BootNet is configured off.
<P>
If you wish to access Level 4 and your Ethernet cards contain
DCI2 modules, configure BootNet off and use the copy of !BootNet
provided.
<P>
If you are running a full TCP/IP network, communicating with NFS
servers, for example, then you should ensure that the file<TT><FONT FACE="Courier">
!BootNet.!Configure</FONT></TT> does not re-load the driver. See
the comments inside that file for full information. The Release
Note contains hints and tips about this.
<H2><A NAME="Set">Set</A>Station</H2>
<P>
Specifically designed to assist discless client start-up, SetStation
sets the full four byte IP address in CMOS RAM. This is required
if a client is connected to a fully-configured TCP/IP network,
as would be the case if you were connected to the Internet via
an ISDN Router. The new Bootnet module checks for a valid AUN
(if BootNet is configured on) or full TCP/IP address (if configured
off) if it finds valid numbers.
<P>
Note that a Power-On Delete will wipe the top three bytes of the
IP address, which will have to be reset if this occurs.
<H2><A NAME="Disc">Disc</A>less client stations</H2>
<P>
If you have discless client stations on your network, you can
configure them to boot from a suitable server. For Level 4 and
Acorn Access network protocols, this procedure is described in
the Level 4 and Access documentation. See also the Appendix <A HREF="10_AppxD">OmniClient and discless workstations</A>.
<P>
Briefly, any client machine containing an Ethernet card with AUN
software is able to boot from a Level 4 server. The following
commands:
<P>
<TT><FONT FACE="Courier">*Configure boot<BR>
*Configure filesystem net<BR>
*Configure fs Server1</FONT></TT>
<P>
will make a machine attempt to log on to a fileserver named `Server1"
as user `Boot' and attempt to run a file or application entitled
!ArmBoot. Ensure the user boot has the option set to `Run'.
<P>
Similarly, for Acorn Access the commands would be:
<P>
<TT><FONT FACE="Courier">*Configure boot<BR>
*Configure filesystem share</FONT></TT>
<P>
and the leftmost of the shared discs on the icon bar is used.
The client machine looks for a file or application called !Shareboot
and attempts to run it. To boot from a shared disc, you will of
course need to have an Acorn Access card fitted to your machine.
<P>
You can use a shared disc to load a copy of OmniClient and then
establish a link to an NT server. However, if you buy an Ethernet
card with OmniClient on board, you may boot from an NT Server
directly.
<P>
To boot from an NT Server, you must first decide whether you wish
to use NetBEUI or IP as the underlying protocol - both are supported
by NT. NetBEUI is lightweight and fast, but IP is more robust
and is suitable for networks with gateways and routers in them.
<P>
Then configure the client station, for example
<P>
<TT><FONT FACE="Courier">*Configure boot<BR>
*Configure filesystem Lanman<BR>
*Configure fs Server2</FONT></TT>
<P>
and ensure there is an application or file !ArmBoot available
on the server which then runs a copy of !Omni, to set up the user
environment.<BR>
<P>
<A HREF="2_useomni"><IMG SRC="pics/PREV.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="Front"><IMG SRC="pics/FRONT.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="TOC"><IMG SRC="pics/CONTS.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="index"><IMG SRC="pics/INDEX.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="4_TCPintro"><IMG SRC="pics/NEXT.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<P>
</BODY>
</HTML>